Skip to content

docs(readme): show the SSO-only (basic_login:false) config + when to use it#17

Merged
BorisTyshkevich merged 1 commit into
mainfrom
docs/credentials-sso-only
Jun 22, 2026
Merged

docs(readme): show the SSO-only (basic_login:false) config + when to use it#17
BorisTyshkevich merged 1 commit into
mainfrom
docs/credentials-sso-only

Conversation

@BorisTyshkevich

Copy link
Copy Markdown
Collaborator

Follow-up to #16. The "Credentials login" section described basic_login: false in prose but only had a credentials-only JSON example — nothing showing how to hide the password path on an OAuth-only cluster.

This adds:

  • an SSO-only example"basic_login": false set alongside idps;
  • a one-line rationale — hide it when the cluster has no password-authenticated CH users (pure JWT via token_processor/verifier), where the path would just 401. Notes that some verifier setups do pass real CH users through (e.g. github.demo accepts its demo user), so the decision is about what the server authenticates, not just "does it use OAuth";
  • the credentials-only config shown simply as {}.

Docs only — no code, no build/test impact.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QennTvGKAtJZrv9EpQagef

…use it

The credentials section described `basic_login:false` in prose but only gave a
credentials-only JSON example. Add the missing SSO-only example (the flag set
alongside `idps`) and a one-line rationale — hide the password path when the
cluster has no password-authenticated CH users (pure JWT), noting that some
verifier setups still pass real CH users through, so it's about what the server
authenticates, not merely "uses OAuth". Also show the credentials-only config as
just `{}`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QennTvGKAtJZrv9EpQagef
@BorisTyshkevich BorisTyshkevich merged commit 82da0f0 into main Jun 22, 2026
2 checks passed
@BorisTyshkevich BorisTyshkevich deleted the docs/credentials-sso-only branch June 22, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant